Identification of a poorly parked vehicle and performance of a first group of actions to cause one or more other devices to perform a second group of actions

ABSTRACT

A device can receive parking metadata that includes location data indicating that a portion of a vehicle is located outside of a designated parking area (DPA). The device can process the parking metadata to identify values that are to be used when determining actions to perform. The device can obtain supplemental events data associated with events occurring near the DPA. The device can determine the actions to perform based on the parking metadata and the supplemental events data. The device can provide, as one of the actions and to one or more other devices or to the vehicle, a message indicating that the portion of the vehicle is located outside of the DPA. This can cause the one or more other devices or the vehicle to: move the vehicle from the DPA, reposition the vehicle within the DPA, or penalize an owner of the vehicle.

BACKGROUND

Parking is the act of stopping and disengaging a vehicle and leaving thevehicle unoccupied. A vehicle can be parked in a parking garage, in aparking lot, on a road in a designated parking spot, and/or the like.Geolocation involves the identification or estimation of a real-worldgeographic location of an object (e.g., a vehicle).

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1C are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, can be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process for identifying a vehiclein a designated parking area as being poorly parked and performingactions for ensuring that the vehicle does not interfere with trafficnear the designated parking area and/or actions for penalizing an owner(or a driver) for poorly parking the vehicle.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

A vehicle can be parked in a parking garage, in a parking lot, on a roadin a designated parking space, and/or the like. In some cases, a roadwith designated parking spots can also include a bicycle lane, an areafor a tram, and/or the like. To fit spaces for multiple lanes oftraffic, a bicycle lane, an area for a tram, a bus lane, and/or thelike, a space reserved for the designated parking spaces might need tobe reduced in size.

However, using the road for too many activities and/or reducing the sizeof the designated parking spaces causes safety concerns. For example, ifa vehicle is poorly parked in a designated parking space that has areduced size (e.g., to provide space for road traffic, a tram, a bicyclepath, a bus, and/or the like), the vehicle might encroach on a part ofthe road that is reserved for other vehicles (e.g., a part of the roadreserved for ordinary traffic, a bicycle, a tram, a bus, and/or thelike). This increases a chance of accidents on the road, causes trafficcongestion, and/or the like.

Some implementations described herein provide a road management platformto receive parking metadata indicating that a vehicle is poorly parkedin a designated parking area and to perform actions to ensure that thevehicle does not interfere with traffic near the designated parking areaand/or actions to penalize an owner (or a driver) for poorly parking thevehicle. For example, the road management platform can receive parkingmetadata for a vehicle that is located at least partially within adesignated parking area. The parking metadata can include location dataindicating that part of the vehicle is located outside of the designatedparking area. Additionally, the road management platform can obtainsupplemental events data associated with one or more events occurringnear the designated parking data (e.g., scheduling data for a tram orbus, traffic data associated with a bicycle lane, and/or the like).

In some implementations, the road management platform can determine afirst group of actions that are to be performed based on the parkingmetadata and the supplemental events data. For example, the roadmanagement platform can be configured with a list of actions that ensurethat the vehicle does not obstruct traffic near the designated parkingarea and/or that penalize an owner (or a driver) for poorly parking thevehicle. In this case, the road management platform can intelligentlydetermine to perform the first group of actions, of the list of actions,based on values included in the parking metadata and/or the supplementalevents data. Additionally, the road management platform, as part ofperforming the first group of actions, can generate and provide amessage to one or more other devices or to the vehicle indicating thatpart of the vehicle is located outside of the designated parking area.This can cause the one or more other devices to perform a second groupof actions to move the vehicle from the designated parking area,reposition the vehicle to be appropriately parked within the designatedparking area, penalize the owner (or the driver) for poorly parking thevehicle, and/or the like.

By performing the first group of actions, the road management platformensures that the vehicle does not interfere or obstruct traffic near thedesignated parking area, thereby reducing accidents, reducing trafficcongestion, and/or the like. This conserves resources (e.g., processingresources, network resources, and/or the like) of first responderdevices used to provide assistance during an accident, conserves fuel byreducing the traffic congestion, and/or the like. Furthermore,penalizing the owner (or the driver) for poorly parking the vehiclereduces future accidents and/or traffic congestion by creating adeterrent that causes subsequent drivers to correctly park theirvehicles in the designated parking area (e.g., or else receive a ticketor be towed).

Furthermore, several different stages of the process for ensuring that aparked vehicle does not interfere with traffic near the designatedparking area are automated, which removes human subjectivity and wastefrom the process, and which improves speed and efficiency of the processand conserves computing resources (e.g., processor resources, memoryresources, and/or the like). For example, by automating the process foridentifying whether the vehicle is appropriately parked within thedesignated parking area, and further automating the process forperforming actions to ensure that the vehicle does not interfere withtraffic near the designated parking area, the road management platformconserves computing resources relative to an inferior device or platformthat has to be used in conjunction with manual assistance. Additionally,implementations described herein use a rigorous, computerized process toperform tasks or roles that were not previously performed or werepreviously performed using subjective human intuition or input.

FIGS. 1A-1C are diagrams of an example implementation 100 describedherein. For example, example implementation 100 can include a reportingdevice (shown as Reporting Device A), a group of parked vehicles (shownas Vehicle A, Vehicle B, Vehicle C, and Vehicle D), a road managementplatform, a data storage device, a moving vehicle (shown as Vehicle E),a user device, a group of secondary systems (shown as a Video ManagementSystem, a Towing Company System, . . . , System M), and a group ofadditional devices (e.g., a speaker, a kiosk, and/or the like). Whileimplementations described herein show a single reporting device, it isto be understood that this is provided by way of example. In practice,the road management platform can interact with one or more sets ofreporting devices that are able to monitor any number of differentdesignated parking areas.

As shown in FIG. 1A, and by reference number 105, the road managementplatform can provide configuration information to the reporting device.For example, the reporting device can be tasked with monitoring adesignated parking area and can be configured using configurationinformation that allows the reporting device to monitor the designatedparking area to determine whether a vehicle is improperly parked.

The configuration information can include a parking area identifier forthe designated parking area, information identifying a set of geographiccoordinates that define boundaries of the designated parking area,information identifying a particular boundary of the designated parkingarea as a boundary that a vehicle is not permitted to encroach or parkover (shown as a keep out zone boundary), information identifyingadditional sets of geographic coordinates that define specific areas(e.g., parking spaces) within the designated parking area (shown byvertical dotted lines), one or more identifiers for the specific areas,a threshold reporting value indicating when to report a vehicle forimproper parking (e.g., when the vehicle encroaches or parks over thekeep out zone boundary, when the vehicle encroaches or parks over thekeep out zone boundary by a threshold distance, etc.), and/or the like.By configuring the reporting device with the configuration informationand one or more features capable of detecting a vehicle within thedesignated parking area, the reporting device can determine whether thevehicle is appropriately parked within the designated parking area, asdescribed further herein.

In some implementations, the road management platform can configure thereporting device using configuration information that is input via aninterface. For example, a user can interact with an interface (e.g., aprogram interface, a web interface, and/or the like) of a user device(e.g., a desktop computer, a mobile device, and/or the like) to inputthe configuration information. In this case, the interface can display amap that includes the designated parking area, and the user can inputthe configuration information into fields of the interface. For example,the user can add boundaries of the designated parking area to the map,such as by drawing a line with a mouse cursor, by inputting geographiccoordinates of the line, and/or the like. Additionally, the user canselect one of the boundaries as the particular boundary identifying thearea that a vehicle is not permitted to encroach or park over (e.g., thekeep out zone boundary), can select a threshold reporting value, and/orthe like. When the user finishes inputting the configuration information(e.g., by selecting a complete or send button), the configurationinformation can be provided to the road management platform which canprovide the configuration information to the reporting device.

In some implementations, the boundaries of the designed parking area canbe pre-configured, and the user can simply add a boundary identifyingthe area that the vehicle is not permitted to encroach or park over. Insome implementations, a device other than the road management platformcan configure the reporting device.

In the example shown in FIG. 1A, a road can have a designated parkingarea located on a side of the road. In this example, a user mightinteract with an interface to add two boundaries of the designatedparking area (shown as two straight lines). One of the boundaries (shownas the keep out zone boundary) can identify an area that vehicles arenot permitted to encroach or park over (e.g., an area closest to theremainder of the road). Additionally, the user can configure a thresholdreporting value which might identify a distance that, if encroached orparked over by a vehicle, would trigger the reporting device to provideparking metadata to the road management platform.

As shown by reference number 110, the reporting device can monitor thedesignated parking area to obtain parking metadata. For example, thereporting device can monitor the designated parking area by recording avideo of the designated parking area, by periodically taking images ofthe designated parking area, and/or the like.

The parking metadata can include identification data, location data,time data, and/or the like. The identification data can include anidentifier of the designated parking area, an identifier of a specificarea (e.g., a parking space) within the designated parking area, anobject identifier for a type of object within the designated parkingarea (e.g., an identifier for a vehicle, motorcycle, etc.), and/or thelike. The location data can include data identifying a set of geographiccoordinates of the designated parking area (e.g., geographic coordinatesdefining the keep out zone boundary), data identifying a set ofgeographic coordinates of the specific parking area within thedesignated parking area (e.g., the parking space), data identifying aset of geographic coordinates of an object (e.g., a vehicle) that is atleast partially inside of the designated parking area, data identifyinga set of geographic coordinates of a portion of the object that isoutside of the designated parking area, and/or the like. As describedherein, a set of geographic coordinates can refer to one or more groupsof coordinates that include a latitudinal coordinate, a longitudinalcoordinate, an altitudinal coordinate, and/or the like. The time datacan include data identifying a time at which a vehicle is identified asbeing located at least partially within the designated parking area.

In some cases, the reporting device can be configured to capturelocation data identifying a set of geographic coordinates of a portionof the vehicle that is outside of the designated parking area. In othercases, the reporting device can determine that a portion of the vehicleis outside of the designated parking area. For example, the reportingdevice can compare location data identifying a set of geographiccoordinates of the designated parking area and location data identifyinga set of geographic coordinates of a vehicle to determine location dataidentifying a set of geographic coordinates of the portion of thevehicle that is outside of the designated parking area.

In some implementations, the reporting device can obtain parkingmetadata by recording a video of the designated parking area. Forexample, the reporting device can record a video of the designatedparking area, which can create a multimedia file of the video. In thiscase, the reporting device can convert the multimedia file to a set ofimage files and can process the image files to generate parking metadatabased on contents of the set of image files.

Additionally, or alternatively, the reporting device can periodicallycapture images of the designated parking area. For example, thereporting device can periodically capture images of the designatedparking area and can process image files to generate parking metadatabased on contents of the image files, as described above. In this way,the reporting device conserves processing resources and/or storageresources relative to recording a video of the designated parking area.

In some implementations, the reporting device can obtain parkingmetadata that satisfies a threshold level of accuracy. For example, thereporting device can monitor the designated parking area to detect athree-dimensional (3-D) object (e.g., a vehicle) that is geolocatedwithin the designated parking area, whereby the location dataidentifying a set of geographic coordinates of the vehicle can satisfy athreshold level of accuracy. As an example, the reporting device cangenerate location data that is within at least 30 centimeters of anactual location of the vehicle. By receiving parking metadata thatsatisfies the threshold level of accuracy, the road management platformis able to process the parking metadata and make intelligent decisionsregarding preforming particular actions that ensure that the vehicledoes not interfere with traffic near the designated parking area, asdescribed further herein.

Additionally, or alternatively, another device can obtain the parkingmetadata. For example, another type of sensor, a vehicle on the road, auser device on or near the road, and/or the like, can obtain the parkingmetadata, in a manner similar to that described above. As a particularexample, a vehicle (e.g., an autonomous vehicle or a partiallyautonomous vehicle capable of self-parking) can generate parkingmetadata when the vehicle parks and can provide the parking metadata tothe road management platform for further processing.

In some implementations, the reporting device can store the parkingmetadata. For example, the reporting device can store the parkingmetadata using a data structure, such as a linked-list, an array, adatabase (e.g., a relational database), a tree, a hash table, and/or thelike. In some implementations, the reporting device can store theparking metadata for a particular time period and can remove (i.e.,delete) the parking metadata after the particular time period.

In this way, the reporting device monitors and obtains parking metadatathat can be used for further processing, as described herein.

As shown in FIG. 1B, and by reference number 115, the reporting devicecan determine that a reporting trigger is satisfied. For example, thereporting device can be configured to determine whether a reportingtrigger that, if satisfied, can cause the reporting device to providethe parking metadata to the road management platform. The reportingtrigger can be one or more threshold values that represent an area inwhich a vehicle is not permitted to be positioned or not permitted toencroach or park over, a time period, an occurrence of a non-zero value(e.g., to report parking metadata every time that parking metadata isobtained and a vehicle is present), and/or the like.

As an example, assume the reporting trigger is satisfied if a positionof the vehicle encroaches or is parked over the geographic coordinatesof the keep out zone boundary. In this example, the reporting device canobtain parking metadata that includes location data identifyinggeographic coordinates of the vehicle and can compare the location dataof the vehicle to location data identifying the geographic coordinatesof the keep out zone boundary to determine that the reporting trigger issatisfied.

As shown by reference number 120, the reporting device can provide theparking metadata to the road management platform. For example, thereporting device can provide the parking metadata based on the reportingtrigger being satisfied. In this case, the reporting device can providethe parking metadata to the road management platform using acommunication interface, such as an application programming interface(API), an interface supported by an internet of things (IoT) protocol,and/or the like.

As shown by reference number 125, the road management platform canobtain supplemental events data. For example, the road managementplatform can obtain supplemental events data periodically over timebased on receiving the parking metadata from the reporting device and/ora similar type of trigger.

The supplemental events data can include scheduling data identifying alocation of a transit vehicle (i.e., a vehicle that is part of a transitservice, such as a bus, a tram, and/or the like) that runs adjacent tothe designated parking area, traffic data identifying traffic in abicycle lane or a roadway that is adjacent to the designated parkingarea, weather data identifying a weather condition in a vicinity of thedesignated parking area, and/or the like. The supplemental events datacan be used to determine a first group of actions to perform, as furtherdescribed below.

In some implementations, the road management platform can obtain thescheduling data identifying the location of the transit vehicle. Forexample, the road management platform can use a data mining technique toanalyze a website and obtain the scheduling data. In this case, the roadmanagement platform can use a natural language processing technique tofurther process the scheduling data to identify a first value thatrepresents a current time and a second value that represents a locationof the transit vehicle.

In some cases, the scheduling data might represent a tentative scheduleand might not identify an actual position of the transit vehicle. Inthis case, the road management platform can use the data miningtechnique to analyze a different website to obtain map data identifyinga real-time image of an area that includes the designated parking area.Additionally, the road management platform can process the map data toidentify an actual position of the transit vehicle.

Additionally, or alternatively, the road management platform can obtainthe traffic data identifying the traffic in the bicycle lane or theroadway that is adjacent to the designated parking area. For example,the road management platform can obtain the traffic data in a mannersimilar to that described above (e.g., using the data mining technique).The traffic data can identify a volume of traffic in the bicycle lane, avolume of traffic in the roadway, and/or the like.

Additionally, or alternatively, the road management platform can obtainthe weather data identifying the weather condition near the designatedparking area. For example, the road management platform can obtain theweather data in a manner similar to that described above (e.g., usingthe data mining technique). The weather data can identify a temperature,a presence of rain, snow, thunder, lightning, and/or the like.

As shown by reference number 130, the road management platform candetermine to perform a first group of actions. For example, the roadmanagement platform can be configured to perform a list of actions andcan select a first group of actions to perform, from the list ofactions, based on values included in the parking metadata and/or thesupplemental events data.

The list of actions can include a first action to generate a messageindicating that a portion of the vehicle is located outside of thedesignated parking area, a second action to provide the message to oneor more other devices, a third action to update a data stream thatprovides a client organization with access to a real-time feed of thedesignated parking area, and/or the like. In some implementations, themessage that is to be generated as the second action can includegeographic coordinates identifying a degree to which the vehicle hasencroached or parked over a boundary of the designated parking area(e.g., the keep out zone boundary).

Additionally, or alternatively, the message can include instructionsthat recommend or enable other devices to perform a second group ofactions. In this case, the road management platform can generate theinstructions that are part of the message and can select the otherdevices that are to be recipients of the message (e.g., based on thevalues included in the parking metadata and/or the supplemental eventsdata). The message can include a first set of instructions to move thevehicle from the designated parking area, a second set of instructionsto reposition the vehicle to be appropriately parked within thedesignated parking area, a third set of instructions to modify a speedor a route of a transit vehicle that is expected to travel adjacent tothe designated parking area to assist the transit vehicle in avoiding acollision with the vehicle, a fourth set of instructions to penalize anowner of the vehicle for improperly parking the vehicle within thedesignated parking area (e.g., by issuing a parking ticket, by towingthe vehicle, etc.), a fifth set of instructions to display or project amessage indicating that the vehicle has to be moved from the designatedparking area or repositioned within the designated parking area, and/orthe like.

In some implementations, the road management platform can use machinelearning to determine the first group of actions to perform. Forexample, the road management platform can train a data model onhistorical data (e.g., historical parking metadata, historicalsupplemental events data, and/or the like) and by using one or moremachine learning techniques to allow the data model to output a set ofvalues that can be used to score (e.g., rank) the list of actions.

The following example illustrates a manner in which the data model mighthave been trained. For example, to train the data model, the roadmanagement platform can standardize and/or cleanse the historical datato transform the historical data into a format that is capable of beingused by the data model. As an example, the historical data can includetext values, integer values, and/or the like, and the road managementplatform can convert all (or some) values to a uniform data type and/orfile format, such that historical data can be used to train the datamodel.

Continuing with the example, the road management platform can determinea set of features that are capable of being used to train the datamodel. For example, the road management platform can determine a set offeatures by providing the historical data to a subject matter expertand/or by using a feature determination technique. The set of featurescan serve as indicators of whether an action is more, or less, likely tobe a preferred action to perform. The feature determination techniquecan include a trend variable analysis, a composite indicators analysis,a clustering analysis, a regression analysis, a statistical model (e.g.,a general linear model), an analysis using a neural network, and/or thelike.

To provide a few examples, the road management platform can use thefeature determination technique to process the historical data todetermine that a distance between a vehicle that is partially inside ofthe designated parking area and another vehicle (e.g., a tram, a bus,and/or the like) serves as an indicator of whether to perform aparticular action. For example, as the distance between the vehicle andthe transit vehicle is reduced, and a collision becomes more imminent,an action to alert the transit vehicle to stop or to slow down becomesmore important because the action might be necessary to avoid acollision.

As another example, the road management platform can use the featuredetermination technique to process the historical data to determine thata degree to which the vehicle is outside of the designated parking areacan serve as an indicator of whether to perform a first action or asecond action. For example, if a vehicle is parked slightly outside ofthe designated parking area, but would not cause a collision with thetram, a first action to ticket a driver or owner of the vehicle might bepreferred to an action to tow the vehicle or to alert a conductor of thetram.

As another example, the road management platform can use the featuredetermination technique to process the historical data to determine thatan indicator of whether the vehicle is an autonomous vehicle capable ofcommunicating with the road management platform might serve as anindicator of whether to perform a first action or a second action. Forexample, if the vehicle is an autonomous vehicle capable ofcommunicating with the road management platform, a first action toprovide the vehicle with instructions to automatically re-park might bepreferred to a second action instructing a tow truck to remove thevehicle from the designated parking area.

As another example, the road management platform can use the featuredetermination technique to process the historical data to determinewhether the vehicle is parked over a boundary adjacent to the designatedparking area (e.g., the keep out zone boundary) or is parked over aboundary perpendicular to the designated parking area (e.g., over one ofthe dotted lines signifying a boundary between two parking spaces) andmight use this information as an indicator of whether to perform a firstaction or a second action. For example, if a vehicle is parked over thekeep out zone boundary, a first action to tow the vehicle or alert atram might be preferred over a second action to issue a parking ticket.Conversely, the second action to issue the parking ticket might bepreferred over the first action if the vehicle is simply parked over theboundary perpendicular to the designated parking area (e.g., the dottedline).

The features described above are provided by way of example. Inpractice, the road management platform can determine tens, hundreds,thousands, or more, of features that can be used to determine whichactions to perform.

In some implementations, the road management platform can use the datamodel to determine the first group of actions to perform. For example,the road management platform can provide the parking metadata and/or thesupplemental events data as input to the data model to cause the datamodel to output a set of values (e.g., scores) that are associated withthe list of actions. In this case, the road management platform canidentify one or more values, of the set of values, that satisfy athreshold confidence level. The one or more values can be stored inassociation with identifiers of actions that can be used as the firstgroup of actions to perform. Furthermore, the road management platformcan select the first group of actions based on the first group ofactions being stored in association with the one or more valuesidentified as satisfying the threshold confidence level.

In some implementations, the road management platform can use a set ofrules to determine the first group of actions to perform. For example,the road management platform can be configured with a set of rules thatassociate actions with particular ranges of parking metadata valuesand/or supplemental events data values, a set of rules that causeparticular actions to be performed if particular parking metadata valuesand/or supplemental events data values are present, and/or the like. Inthis case, the road management platform can determine the first group ofactions to perform by referencing the set of rules to identify whichactions are associated with parking metadata values and/or supplementalevents data values that have been received and/or obtained. As anexample, a rule might indicate that a message is to be immediatelygenerated and provided to a transit vehicle if the transit vehicle iswithin a threshold distance of the vehicle and is traveling adjacent tothe designated parking area.

In this way, the road management platform determines the first group ofactions to perform. Furthermore, by considering the supplemental eventsdata when determining the first group of actions to perform, the roadmanagement platform conserves resources (e.g., processing resources,network resources, and/or the like) relative to an inferior platformthat is unable to consider supplemental events data. For example,supplemental events data might indicate that a tram is within athreshold distance of the designated parking area, which might cause theroad management platform to perform a first action (e.g., instruct a towtruck to remove the vehicle) when an inferior platform without access tothe supplemental events data might generate a second action (e.g., issuea parking ticket). The second action might not prevent a collision, andmight cause devices used to assist with the accident to expendprocessing resources and/or network resources while performing firstresponder duties, might cause traffic congestion to nearby vehicles(e.g., which might then waste fuel resources, expend resources using anavigational resources to identify a new route based on the trafficcongestion, etc.), and/or the like.

As shown in FIG. 1C, and by reference number 135, the road managementplatform can, as part of the first group of actions, generate themessage indicating that a portion of the vehicle is located outside ofthe designated parking area. As shown by reference number 140, the roadmanagement platform can provide the message to another device. As shownby reference number 145, receiving the message can cause the otherdevice to perform a second group of actions to ensure that the vehicledoes not interfere with traffic near the designated parking area and/orto penalize an owner (or a driver) for poorly parking the vehicle.Several examples of generating and providing a particular device with aparticular message are provided below.

In some implementations, the road management platform can generate andprovide the user device and/or the vehicle with a first message thatincludes the first set of instructions indicating to move the vehiclefrom the designated parking area. For example, the road managementplatform can generate and provide the user device and/or the vehiclewith the first message to alert an owner of the vehicle that the vehicleneeds to be moved from the designated parking area. In some cases, thefirst message can include further instructions indicating that the ownerof the vehicle might be ticketed, or that the vehicle might be towed ifthe vehicle is not moved within a threshold time period. This can causethe user to manually remove the vehicle from the designated parkingarea, to interact with the user device to provide instructions thatcause the vehicle to automatically remove itself from the designatedparking area, or can cause the vehicle to automatically remove itselffrom the designated parking area (e.g., without instructions from theuser).

Additionally, or alternatively, the road management platform cangenerate and provide the vehicle with a second message that includes thesecond set of instructions to reposition the vehicle to be appropriatelyparked within the designated parking area. For example, the roadmanagement platform can generate, as part of the second message,instructions indicating to reposition the vehicle, instructionsindicating how to reposition the vehicle, instructions indicating adegree to which the vehicle needs to be repositioned, and/or the like.In some cases, the instructions can allow an autonomous vehicle toautomatically reposition itself to be appropriately parked within thedesignated parking area.

Additionally, or alternatively, the road management platform cangenerate and provide the moving vehicle (shown as Vehicle E) with athird message that includes the third set of instructions to modify aspeed or a route of the moving vehicle. This can allow the movingvehicle to avoid traveling on a part of the roadway that is adjacent tothe designated parking area, to slow down to give the vehicle time toreposition itself or to be moved from the designated parking area,and/or the like. As an example, if the moving vehicle is part of anorganization that contracts with an organization that manages the roadmanagement platform (e.g., a transportation or shipping organization),then the road management platform might be able to communicate with themoving vehicle to allow the moving vehicle to modify the speed or theroute.

Additionally, or alternatively, the road management platform cangenerate and provide the third message that includes the third set ofinstructions to a transit vehicle, a device associated with anindividual riding a bicycle, and/or the like. For example, the roadmanagement platform can provide the third message to a transit vehiclethat shares the roadway with other traffic to notify the transit vehiclethat the designated parking area includes a vehicle that might obstructa path of the transit vehicle. In this case, the third message mightinclude instructions indicating a predicted time at which a collisionwould occur if the vehicle remains positioned in the designated parkingarea, a recommended reduced speed of the transit vehicle (e.g., to giveVehicle C time to repark), an alternative path that can be taken by thetransit vehicle, and/or the like. In some cases, the instructions mightbe based on the supplemental events data. For example, the weather datamight indicate a certain amount of precipitation, which might increase astopping time needed to stop the transit vehicle, which might decrease arecommended reduced speed that the transmit vehicle is to travel, and/orthe like. A similar message can be generated and provided to theindividual riding the bicycle to notify the individual of theobstruction (e.g., the similar message can be provided to a media playeraffixed to the individual).

Additionally, or alternatively, the road management platform cangenerate and provide the one or more secondary systems with a fourthmessage that includes the fourth set of instructions to penalize anowner (or a driver) of the vehicle for improperly parking the vehiclewithin the designated parking area. For example, the road managementplatform can generate the fourth message to include instructionsindicating a current position of the vehicle, a recommended action toperform (e.g., ticket the vehicle, tow the vehicle, and/or the like), arecommended time by which to perform the recommended action, and/or thelike.

Additionally, or alternatively, the road management platform cangenerate and provide the additional devices (e.g., the speaker, andkiosk, and/or the like) with a fifth message that includes the first orsecond set of instructions. For example, the road management platformcan generate an audio message that can be projected near the vehicle viathe speaker and/or the kiosk, can generate a text message that can bedisplayed via an interface of the kiosk (e.g., which, for example, anindividual might view when paying for parking), and/or the like.

Additionally, or alternatively, while not shown, the road managementplatform can update a data stream that provides a real-time feed of thedesignated parking area. For example, the road management platform canupdate a data stream that is accessible by one or more of the secondarysystems. This can allow a secondary system, such as a video managementsystem or a towing company system, to use the real-time feed of thedesignated parking area to perform the second group of actions. Forexample, a server associated with the towing company system can displaythe real-time feed, and can, based on detecting that the real-time feedis indicating that the vehicle is parked outside of the designatedparking area, generate and provide instructions to a tow truck to towthe vehicle from the designated parking area. As another example, aserver associated with the video management system can display thereal-time feed, and can, based on detecting that the real-time feedindicates that the vehicle is parked outside of the designated parkingarea, provide instructions to a device accessible to an individual thatassigns parking tickets to permit the individual to issue the vehicle aparking ticket. In some cases, fields of an electronic parking ticketcan be automatically populated based on a device associated with asecondary system receiving the message.

By performing the first group of actions, the road management platformensures that the vehicle does not interfere or obstruct traffic near thedesignated parking area, thereby reducing accidents, reducing trafficcongestion, and/or the like. This conserves resources (e.g., processingresources, network resources, and/or the like) of first responderdevices used to provide assistance during an accident, conserves fuel byreducing the traffic congestion, and/or the like. Furthermore,penalizing the owner (or the driver) for poorly parking the vehiclereduces future accidents and/or traffic congestion by creating adeterrent that causes subsequent drivers to correctly park theirvehicles in the designated parking area (e.g., or else receive a ticketor be towed).

As indicated above, FIGS. 1A-1C are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIGS. 1A-1C. For example, there can be additional devices and/ornetworks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIGS. 1A-1C. Furthermore, two or more devices shown in FIGS.1A-1C can be implemented within a single device, or a single deviceshown in FIGS. 1A-1C can be implemented as multiple, distributeddevices. Additionally, or alternatively, a set of devices (e.g., one ormore devices) of example implementation 100 can perform one or morefunctions described as being performed by another set of devices ofexample implementation 100.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include a reporting device 210, a data storagedevice 220, a road management platform 230 hosted within a cloudcomputing environment 240, a user device 250, and/or a network 260.Devices of environment 200 can interconnect via wired connections,wireless connections, or a combination of wired and wirelessconnections.

Reporting device 210 includes one or more device capable of obtaining,storing, and/or providing information associated with a designatedparking area. In some implementations, reporting device 210 can be adevice with a sensor that is capable of detecting objects, motion,weather, and/or the like, a vehicle (e.g., a car, a truck, a plane, adrone, an autonomous vehicle, and/or the like), a user device (e.g., acommunication device, such as a mobile phone), and/or the like. Forexample, reporting device 210 can include a camera (e.g., a visualspectrum imaging camera, an infrared or near infrared imaging camera, amulti spectral imaging camera, a hyperspectral imaging camera, a thermalimaging camera, a laser mapping imagery camera, a camera capable ofdetecting vehicles in a designated parking area, etc.), a speeddetecting device, and/or the like.

In some implementations, reporting device 210 can monitor a designatedparking area to obtain parking metadata. In some implementations,reporting device 210 can include a sensor capable of obtaining parkingmetadata of a vehicle that is accurate within at least 30 centimeters ofan actual location of the vehicle. In some implementations, reportingdevice 210 can receive configuration information from road managementplatform 230 or another device. In some implementations, reportingdevice 210 can provide parking metadata to road management platform 230and/or data storage device 220.

Data storage device 220 includes one or more devices capable ofreceiving, storing, generating, determining, and/or providinginformation associated with one or more sets of designated parkingareas. For example, data storage device 220 can include a server deviceor a group of server devices. In some implementations, data storagedevice 220 can store supplemental events data. In some implementations,data storage device 220 can provide supplemental events data to roadmanagement platform 230. In some implementations, a first data storagedevice 220 can store and/or provide scheduling data identifying alocation of a transit vehicle to road management platform 230.Additionally, or alternatively, a second data storage device 220 canstore and/or provide traffic data identifying traffic in a bicycle lineor roadway to road management platform 230. Additionally, oralternatively, a third data storage device 220 can store and/or provideweather data identifying a weather condition near the designated parkingarea to road management platform 230.

Road management platform 230 includes one or more devices capable ofreceiving, storing, generating, determining, and/or providinginformation associated with a designated parking area. For example, roadmanagement platform 230 can include a server device (e.g., a hostserver, a web server, an application server, etc.), a data centerdevice, or a similar device. In some implementations, road managementplatform 230 can provide configuration information to reporting device210. In some implementations, road management platform 230 can support aprogram (e.g., a website, a mobile application, and/or the like) thatallows a user to interact with an interface to input configurationinformation for reporting device 210. In some implementations, roadmanagement platform 230 can perform a first group of actions thatinclude interacting with one or more other devices to cause the one ormore other devices to perform a second group of actions that improvevehicle positioning or safety within a designated parking area. The oneor more other devices can include reporting device 210, user device 250,a vehicle in a designated parking area, a moving vehicle outside of thedesignated parking area, a secondary system (e.g., a video managementsystem, a towing company system, and/or the like), a speaker, a kiosk,and/or the like.

In some implementations, as shown, road management platform 230 can behosted in cloud computing environment 240. Notably, whileimplementations described herein describe road management platform 230as being hosted in cloud computing environment 240, in someimplementations, road management platform 230 might not be cloud-based(i.e., can be implemented outside of a cloud computing environment) orcan be partially cloud-based.

Cloud computing environment 240 includes an environment that hosts roadmanagement platform 230. Cloud computing environment 240 can providecomputation, software, data access, storage, etc. services that do notrequire end-user knowledge of a physical location and configuration ofsystem(s) and/or device(s) that hosts road management platform 230. Asshown, cloud computing environment 240 can include a group of computingresources 235 (referred to collectively as “computing resources 235” andindividually as “computing resource 235”).

Computing resource 235 includes one or more personal computers,workstation computers, server devices, or another type of computationand/or communication device. In some implementations, computing resource235 can host road management platform 230. The cloud resources caninclude compute instances executing in computing resource 235, storagedevices provided in computing resource 235, data transfer devicesprovided by computing resource 235, and/or the like. In someimplementations, computing resource 235 can communicate with othercomputing resources 235 via wired connections, wireless connections, ora combination of wired and wireless connections.

As further shown in FIG. 2, computing resource 235 can include a groupof cloud resources, such as one or more applications (“APPs”) 235-1, oneor more virtual machines (“VMs”) 235-2, virtualized storage (“VSs”)235-3, one or more hypervisors (“HYPs”) 235-4, and/or the like.

Application 235-1 can include one or more software applications that canbe provided to or accessed by reporting device 210, data storage device220, and/or user device 250. Application 235-1 can eliminate a need toinstall and execute the software applications on these devices. Forexample, application 235-1 can include software associated with roadmanagement platform 230 and/or any other software capable of beingprovided via cloud computing environment 240. In some implementations,one application 235-1 can send/receive information to/from one or moreother applications 235-1, via virtual machine 235-2.

Virtual machine 235-2 can include a software implementation of a machine(e.g., a computer) that executes programs like a physical machine.Virtual machine 235-2 can be either a system virtual machine or aprocess virtual machine, depending upon use and degree of correspondenceto any real machine by virtual machine 235-2. A system virtual machinecan provide a complete system platform that supports execution of acomplete operating system (“OS”). A process virtual machine can executea single program and can support a single process. In someimplementations, virtual machine 235-2 can execute on behalf of anotherdevice (e.g., reporting device 210, data storage device 220, user device250, etc.), and can manage infrastructure of cloud computing environment240, such as data management, synchronization, or long-duration datatransfers.

Virtualized storage 235-3 can include one or more storage systems and/orone or more devices that use virtualization techniques within thestorage systems or devices of computing resource 235. In someimplementations, within the context of a storage system, types ofvirtualizations can include block virtualization and filevirtualization. Block virtualization can refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem can be accessed without regard to physical storage orheterogeneous structure. The separation can permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization can eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This can enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

Hypervisor 235-4 can provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as computing resource 235.Hypervisor 235-4 can present a virtual operating platform to the guestoperating systems and can manage the execution of the guest operatingsystems. Multiple instances of a variety of operating systems can sharevirtualized hardware resources.

User device 250 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith a designated parking area. For example, user device 250 can includea communication and/or computing device, such as a mobile phone (e.g., asmart phone, a radiotelephone, etc.), a laptop computer, a tabletcomputer, a handheld computer, a server computer, a gaming device, awearable communication device (e.g., a smart wristwatch, a pair of smarteyeglasses, etc.), or a similar type of device. In some implementations,user device 250 can be a device of an owner of a vehicle (or driver ofthe vehicle) that is within the designated parking area or that istraveling through a roadway using a path that is obstructed by anothervehicle that is within the designated parking area.

Network 260 includes one or more wired and/or wireless networks. Forexample, network 260 can include a cellular network (e.g., a fifthgeneration (5G) network, a fourth generation (4G) network, such as along-term evolution (LTE) network, a third generation (3G) network, acode division multiple access (CDMA) network, a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300can correspond to reporting device 210, data storage device 220, roadmanagement platform 230, and/or user device 250. In someimplementations, reporting device 210, data storage device 220, roadmanagement platform 230, and/or user device 250 can include one or moredevices 300 and/or one or more components of device 300. As shown inFIG. 3, device 300 can include a bus 310, a processor 320, a memory 330,a storage component 340, an input component 350, an output component360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC),and/or another type of processing component. In some implementations,processor 320 includes one or more processors capable of beingprogrammed to perform a function. Memory 330 includes a random accessmemory (RAM), a read only memory (ROM), and/or another type of dynamicor static storage device (e.g., a flash memory, a magnetic memory,and/or an optical memory) that stores information and/or instructionsfor use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 can permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 300 can perform one or more processes described herein. Device300 can perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 can causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 canperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for identifying avehicle in a designated parking area as being poorly parked andperforming actions for ensuring that the vehicle does not interfere withtraffic near the designated parking area and/or actions for penalizingan owner (or a driver) for poorly parking the vehicle. In someimplementations, one or more process blocks of FIG. 4 can be performedby a road management platform (e.g., road management platform 230). Insome implementations, one or more process blocks of FIG. 4 can beperformed by another device or a group of devices separate from orincluding the road management platform, such as a reporting device(e.g., reporting device 210), a data storage device (e.g., data storagedevice 220), and/or a user device (e.g., user device 250).

As shown in FIG. 4, process 400 can include receiving parking metadatafor a vehicle that is located at least partially within a designatedparking area, wherein the parking metadata includes location dataindicating that a portion of the vehicle is located outside of thedesignated parking area (block 410). For example, the road managementplatform (e.g., road management platform 230, using computing resource235, processor 320, memory 330, input component 350, communicationinterface 370, etc.) can receive parking metadata for a vehicle that islocated at least partially within a designated parking area, asdescribed above with regard to FIGS. 1A-1C. In some implementations, theparking metadata can include location data indicating that a portion ofthe vehicle is located outside of the designated parking area.

As further shown in FIG. 4, process 400 can include processing theparking metadata to identify: a set of geographic coordinates of thedesignated parking area, a time at which the vehicle was identified asbeing located at least partially within the designated parking area, anda degree to which the vehicle is located outside of the set ofgeographic coordinates of the designated parking area (block 420). Forexample, the road management platform (e.g., road management platform230, using computing resource 235, processor 320, memory 330, etc.) canprocess the parking metadata to identify: a set of geographiccoordinates of the designated parking area, a time at which the vehiclewas identified as being located at least partially within the designatedparking area, and a degree to which the vehicle is located outside ofthe set of geographic coordinates of the designated parking area, asdescribed above with regard to FIGS. 1A-1C.

As further shown in FIG. 4, process 400 can include obtainingsupplemental events data associated with one or more events occurring ina vicinity of the designated parking area (block 430). For example, theroad management platform (e.g., road management platform 230, usingcomputing resource 235, processor 320, memory 330, input component 350,output component 360, communication interface 370, etc.) can obtainsupplemental events data associated with one or more events occurring ina vicinity of the designated parking area, as described above withregard to FIGS. 1A-1C.

As further shown in FIG. 4, process 400 can include determining a firstgroup of actions to perform based on the parking metadata and thesupplemental events data (block 440). For example, the road managementplatform (e.g., road management platform 230, using computing resource235, processor 320, memory 330, input component 350, output component360, communication interface 370, etc.) can determine a first group ofactions to perform based on the parking metadata and the supplementalevents data, as described above with regard to FIGS. 1A-1C.

As further shown in FIG. 4, if the road management platform identifiesparking metadata values and supplemental events data values that arewithin a first range of values, process 400 can include providing, aspart of the first group of actions and to one or more other devices orto the vehicle, a message indicating that the portion of the vehicle islocated outside of the designated parking area to cause the one or moreother devices or the vehicle to perform a second group of actions to:move the vehicle from the designated parking area or reposition thevehicle within the set of geographic coordinates of the designatedparking area (block 450). For example, the road management platform(e.g., road management platform 230, using computing resource 235,processor 320, memory 330, output component 360, communication interface370, etc.) can provide, as part of the first group of actions and to oneor more other devices or to the vehicle, a message indicating that theportion of the vehicle is located outside of the designated parking areato cause the one or more other devices or the vehicle to perform asecond group of actions to: move the vehicle from the designated parkingarea or reposition the vehicle within the set of geographic coordinatesof the designated parking area, as described above with regard to FIGS.1A-1C.

As further shown in FIG. 4, if the road management platform identifiesparking metadata values and supplemental events data values that arewithin a second range of values, process 400 can include providing, aspart of the first group of actions and to one or more particulardevices, an update to a data stream that provides a feed of thedesignated parking area to cause the one or more particular devices toperform a second group of actions involving penalizing the owner of thevehicle for a manner in which the vehicle was positioned in thedesignated parking area (block 460). For example, the road managementplatform (e.g., road management platform 230, using computing resource235, processor 320, memory 330, input component 350, output component360, communication interface 370, etc.) can provide, as part of thefirst group of actions and to one or more particular devices, an updateto a data stream that provides a feed of the designated parking area tocause the one or more particular devices to perform a second group ofactions involving penalizing the owner of the vehicle for a manner inwhich the vehicle was positioned in the designated parking area, asdescribed above with regard to FIGS. 1A-1C.

Process 400 can include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the road management platform, when receivingthe parking metadata, can receive the parking metadata from a sensordevice that is configured to determine the location data in a mannerthat is accurate within at least 30 centimeters of an actual location ofthe vehicle. In some implementations, the supplemental events data caninclude scheduling data identifying a location of a particular vehiclethat is part of a transit service that runs adjacent to the designatedparking area, traffic data identifying traffic associated with a bicyclelane or a roadway that is adjacent to the designated parking area,weather data identifying a weather condition at the designated parkingarea, and/or the like.

In some implementations, the road management platform, when determiningthe first group of actions that are to be performed, can provide theparking metadata and the supplemental events data as input to a datamodel to cause the data model to output a set of values that are to beused to score a third group of actions that include the first group ofactions. In some implementations, the road management platform candetermine that one or more values, of the set of values, satisfy aconfidence threshold. The one or more values can be associated with thefirst group of actions. In some implementations, the road managementplatform can determine the first group of actions that are to beperformed based on determining that the one or more values satisfy theconfidence threshold.

In some implementations, the road management platform, when performingthe first group of actions, can generate the message indicating that theportion of the vehicle is located outside of the designated parkingarea. The message can include instructions indicating to modify a speedor a route of a particular vehicle to avoid a collision with thevehicle. The route the particular vehicle is expected to travel can beadjacent to the designated parking area. In some implementations, theroad management platform can provide the message to the particularvehicle to cause the particular vehicle to modify the speed or the routeto avoid the collision with the vehicle.

In some implementations, the road management platform, when performingthe first group of actions, can generate the message indicating that theportion of the vehicle is located outside of the designated parkingarea. The message can include instructions to move the vehicle within orfrom the designated parking area. In some implementations, the roadmanagement platform can provide the message to the vehicle or to theuser device associated with the vehicle (e.g., user device 250) to causethe vehicle to move within the designated parking area or to be movedfrom the designated parking area.

In some implementations, the message can include a first set ofinstructions to move the vehicle from the designated parking area, asecond set of instructions to reposition the vehicle within thedesignated parking area, a third set of instructions to modify a speedor a route of a particular vehicle that is expected to travel adjacentto the designated parking area to assist the particular vehicle inavoiding a collision with the vehicle, a fourth set of instructions topenalize the owner of the vehicle for the manner in which the vehiclewas positioned in the designated parking area, a fifth set ofinstructions to display or project a notification indicating that thevehicle has to be moved within the designated parking area or moved fromthe designated parking area, and/or the like.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 can be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold can refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, or the like.

To the extent the aforementioned embodiments collect, store, or employpersonal information of individuals, it should be understood that suchinformation shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a first device, parking metadata for a vehicle that is located at least partially within a designated parking area, wherein the parking metadata includes location data indicating that a portion of the vehicle is located outside of the designated parking area; processing, by the first device, the parking metadata to identify: a set of geographic coordinates of the designated parking area, a time at which the vehicle was identified as being located at least partially within the designated parking area, and a degree to which the vehicle is located outside of the set of geographic coordinates of the designated parking area; obtaining, by the first device, supplemental events data associated with one or more events occurring in a vicinity of the designated parking area; determining, by the first device, a first group of actions that are to be performed based on the parking metadata and the supplemental events data, wherein the first group of actions include a first action to provide, to one or more other devices or to the vehicle, a message indicating that the portion of the vehicle is located outside of the designated parking area; and performing, by the first device, the first group of actions to cause the one or more other devices or the vehicle to perform a second group of actions to: move the vehicle from the designated parking area, reposition the vehicle within the set of geographic coordinates of the designated parking area, or penalize an owner of the vehicle for a manner in which the vehicle was positioned in the designated parking area.
 2. The method of claim 1, wherein receiving the parking metadata comprises: receiving the parking metadata from a sensor device that is configured to determine the location data in a manner that is accurate within at least 30 centimeters of an actual location of the vehicle.
 3. The method of claim 1, wherein the supplemental events data includes at least one of: scheduling data identifying a location of a particular vehicle that is part of a transit service that runs adjacent to the designated parking area, traffic data identifying traffic associated with a bicycle lane or a roadway that is adjacent to the designated parking area, or weather data identifying a weather condition at the designated parking area.
 4. The method of claim 1, wherein determining the first group of actions that are to be performed comprises: providing the parking metadata and the supplemental events data as input to a data model to cause the data model to output a set of values that are to be used to score a third group of actions that include the first group of actions, determining that one or more values, of the set of values, satisfy a confidence threshold, wherein the one or more values are associated with the first group of actions, and determining the first group of actions that are to be performed based on determining that the one or more values satisfy the confidence threshold.
 5. The method of claim 1, wherein performing the first group of actions comprises: generating the message indicating that the portion of the vehicle is located outside of the designated parking area, wherein the message includes instructions indicating to modify a speed or a route of a particular vehicle to avoid a collision with the vehicle, and wherein the route the particular vehicle is expected to travel is adjacent to the designated parking area, and providing the message to the particular vehicle to cause the particular vehicle to modify the speed or the route to avoid the collision with the vehicle.
 6. The method of claim 1, wherein performing the first group of actions comprises: generating the message indicating that the portion of the vehicle is located outside of the designated parking area, wherein the message includes instructions to move the vehicle within or from the designated parking area, and providing the message to the vehicle or to a user device associated with the vehicle to cause the vehicle to move within the designated parking area or to be moved from the designated parking area.
 7. The method of claim 1, wherein the message includes at least one of: a first set of instructions to move the vehicle from the designated parking area, a second set of instructions to reposition the vehicle within the designated parking area, a third set of instructions to modify a speed or a route of a particular vehicle that is expected to travel adjacent to the designated parking area to assist the particular vehicle in avoiding a collision with the vehicle, a fourth set of instructions to penalize the owner of the vehicle for the manner in which the vehicle was positioned in the designated parking area, or a fifth set of instructions to display or project a notification indicating that the vehicle has to be moved within the designated parking area or moved from the designated parking area.
 8. A first device, comprising: one or more memories; and one or more processors, to: receive parking metadata for a vehicle that is located at least partially within a designated parking area, wherein the parking metadata includes location data indicating that a portion of the vehicle is located outside of the designated parking area; process the parking metadata to identify: a set of geographic coordinates of the designated parking area, a time at which the vehicle was identified as being located at least partially within the designated parking area, and a degree to which the vehicle is located outside of the set of geographic coordinates of the designated parking area; obtain supplemental events data associated with one or more events occurring in a vicinity of the designated parking area; determine a first group of actions that are to be performed based on the parking metadata and the supplemental events data, wherein the first group of actions include a first action to provide, to one or more other devices or to the vehicle, a message indicating that the portion of the vehicle is located outside of the designated parking area; and perform the first group of actions to cause the one or more other devices or the vehicle to perform a second group of actions to: move the vehicle from the designated parking area, reposition the vehicle within the designated parking area, or penalize an owner of the vehicle for a manner in which the vehicle was positioned in the designated parking area.
 9. The first device of claim 8, wherein the one or more processors, when receiving the parking metadata, are to: receive the parking metadata from a sensor device that is configured to determine the location data in a manner that is accurate within at least 30 centimeters of an actual location of the vehicle.
 10. The first device of claim 8, wherein the supplemental events data includes at least one of: schedule data identifying a location of a particular vehicle that is part of a transit service that runs adjacent to the designated parking area, traffic data identifying traffic associated with a bicycle lane or a roadway that is adjacent to the designated parking area, or weather data identifying a weather condition at the designated parking area.
 11. The first device of claim 8, wherein the one or more processors, when determining the first group of actions that are to be performed, are to: provide the parking metadata and the supplemental events data as input to a data model to cause the data model to output a set of values that are to be used to score a third group of actions that include the first group of actions, determine that one or more values, of the set of values, satisfy a confidence threshold, wherein the one or more values are associated with the first group of actions, and determine the first group of actions that are to be performed based on determining that the one or more values satisfy the confidence threshold.
 12. The first device of claim 8, wherein the one or more processors, when performing the first group of actions, are to: generate the message indicating that the portion of the vehicle is located outside of the designated parking area, wherein the message includes instructions indicating to modify a speed or a route of a particular vehicle to avoid a collision with the vehicle, and wherein the route the particular vehicle is expected to travel is adjacent to the designated parking area, and provide the message to the particular vehicle to cause the particular vehicle to modify the speed or the route to avoid the collision with the vehicle.
 13. The first device of claim 8, wherein the one or more processors, when performing the first group of actions, are to: generate the message indicating that the portion of the vehicle is located outside of the designated parking area, wherein the message includes instructions to move the vehicle within or from the designated parking area, and provide the message to the vehicle or to a user device associated with the vehicle to cause the vehicle to move within the designated parking area or to be moved from the designated parking area.
 14. The first device of claim 8, wherein the message includes at least one of: a first set of instructions to move the vehicle from the designated parking area, a second set of instructions to reposition the vehicle within the designated parking area, a third set of instructions to modify a speed or a route of a particular vehicle that is expected to travel adjacent to the designated parking area to assist the particular vehicle in avoiding a collision with the vehicle, a fourth set of instructions to penalize the owner of the vehicle for the manner in which the vehicle was positioned in the designated parking area, or a fifth set of instructions to display or project a notification indicating that the vehicle has to be moved within the designated parking area or moved from the designated parking area.
 15. A non-transitory computer-readable medium storing one or more instructions, the one or more instructions comprising: one or more instructions that, when executed by one or more processors of a first device, cause the one or more processors to: receive parking metadata for a vehicle that is located at least partially within a designated parking area, wherein the parking metadata includes location data indicating that a portion of the vehicle is located outside of the designated parking area; process the parking metadata to identify: a set of geographic coordinates of the designated parking area, a time at which the vehicle was identified as being located at least partially within the designated parking area, and a degree to which the vehicle is located outside of the set of geographic coordinates of the designated parking area; obtain supplemental events data associated with one or more events occurring in a vicinity of the designated parking area; determine a first group of actions that are to be performed based on the parking metadata and the supplemental events data, wherein the first group of actions include a first action to provide, to one or more other devices or to the vehicle, a message indicating that the portion of the vehicle is located outside of the designated parking area; and perform the first group of actions to cause the one or more other devices or the vehicle to perform a second group of actions to: move the vehicle from the designated parking area, reposition the vehicle within the designated parking area, or penalize an owner of the vehicle for a manner in which the vehicle was positioned in the designated parking area.
 16. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the one or more processors to receive the parking metadata, cause the one or more processors to: receive the parking metadata from a sensor device that is configured to determine the location data in a manner that is accurate within at least 30 centimeters of an actual location of the vehicle.
 17. The non-transitory computer-readable medium of claim 15, wherein the supplemental events data includes at least one of: schedule data identifying a location of a particular vehicle that is part of a transit service that runs adjacent to the designated parking area, traffic data identifying traffic associated with a bicycle lane or a roadway that is adjacent to the designated parking area, or weather data identifying a weather condition at the designated parking area.
 18. The non-transitory computer-readable medium of claim 15, wherein determining the first group of actions that are to be performed comprises: provide the parking metadata and the supplemental events data as input to a data model to cause the data model to output a set of values that are to be used to score a third group of actions that include the first group of actions, determine that one or more values, of the set of values, satisfy a confidence threshold, wherein the one or more values are associated with the first group of actions, and determine the first group of actions that are to be performed based on determining that the one or more values satisfy the confidence threshold.
 19. The non-transitory computer-readable medium of claim 15, wherein the one or more instructions, that cause the one or more processors to perform the first group of actions, cause the one or more processors to: generate the message indicating that the portion of the vehicle is located outside of the designated parking area, wherein the message includes instructions to move the vehicle within or from the designated parking area, and provide the message to the vehicle or to a user device associated with the vehicle to cause the vehicle to move within the designated parking area or to be moved from the designated parking area.
 20. The non-transitory computer-readable medium of claim 15, wherein the message includes at least one of: a first set of instructions to move the vehicle from the designated parking area, a second set of instructions to reposition the vehicle within the designated parking area, a third set of instructions to modify a speed or a route of a particular vehicle that is expected to travel adjacent to the designated parking area to assist the particular vehicle in avoiding a collision with the vehicle, a fourth set of instructions to penalize the owner of the vehicle for the manner in which the vehicle was positioned in the designated parking area, or a fifth set of instructions to display or project a notification indicating that the vehicle has to be moved within the designated parking area or moved from the designated parking area. 